| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-S.3.3.3.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.3.3 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | S_3_3_3_Manage_Documents_for_Personal_Representation |
| Title | S.3.3.3 Manage Documents for Personal Representation (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Manage documents that designate those authorized to act on behalf of the PHR Account Holder. |
| Purpose | The PHR Account Holder may want to capture and maintain documents that pertain to designating those authorized to act on behalf of PHR Account Holder for healthcare. Examples include but are not limited to: Guardianship, Legal Custodial Parent, Executor or Trustee. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation that specifies the location of the original (hardcopy or original). |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage documents that designate those authorized to act on behalf of the PHR Account Holder.
The PHR Account Holder may want to capture and maintain documents that pertain to designating those authorized to act on behalf of PHR Account Holder for healthcare. Examples include but are not limited to: Guardianship, Legal Custodial Parent, Executor or Trustee. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation that specifies the location of the original (hardcopy or original).
| S.3.3.3#01 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render Consents, Authorizations, and other documentation authorizing individuals and/or PHR Account Holder Proxies to act on behalf of the PHR Account Holder with regard to healthcare or the PHR-S. |
| S.3.3.3#02 | SHOULD |
The system SHOULD provide the ability to render a list of documents designating those authorized to act on behalf of the PHR Account Holder sorted by one or more defined data elements. |
| S.3.3.3#03 | MAY |
The system MAY provide the ability to tag a document designating those authorized to act on behalf of the PHR Account Holder as Active or Non-Active by category of document. |
| S.3.3.3#04 | SHOULD |
The system SHOULD maintain the document designating those authorized to act on behalf of the PHR Account Holder and/or a note that specifies that document’s location. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-S.3.3.3",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage documents that designate those authorized to act on behalf of the PHR Account Holder.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The PHR Account Holder may want to capture and maintain documents that pertain to designating those authorized to act on behalf of PHR Account Holder for healthcare. Examples include but are not limited to: Guardianship, Legal Custodial Parent, Executor or Trustee. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation that specifies the location of the original (hardcopy or original).</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render Consents, Authorizations, and other documentation authorizing individuals and/or PHR Account Holder Proxies to act on behalf of the PHR Account Holder with regard to healthcare or the PHR-S.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a list of documents designating those authorized to act on behalf of the PHR Account Holder sorted by one or more defined data elements.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to tag a document designating those authorized to act on behalf of the PHR Account Holder as Active or Non-Active by category of document.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.3.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD maintain the document designating those authorized to act on behalf of the PHR Account Holder and/or a note that specifies that document’s location.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.3.3",
"version" : "2.0.1-ballot",
"name" : "S_3_3_3_Manage_Documents_for_Personal_Representation",
"title" : "S.3.3.3 Manage Documents for Personal Representation (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage documents that designate those authorized to act on behalf of the PHR Account Holder.",
"purpose" : "The PHR Account Holder may want to capture and maintain documents that pertain to designating those authorized to act on behalf of PHR Account Holder for healthcare. Examples include but are not limited to: Guardianship, Legal Custodial Parent, Executor or Trustee. The system should allow for multiple occurrences of a document and the ability to archive documents. The documents maintained will depend on the jurisdictional law. The documents may or may not reside in the PHR-S. The document may be scanned images, structured documents or simply a notation that specifies the location of the original (hardcopy or original).",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.3.3-01",
"label" : "S.3.3.3#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render Consents, Authorizations, and other documentation authorizing individuals and/or PHR Account Holder Proxies to act on behalf of the PHR Account Holder with regard to healthcare or the PHR-S."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.3.3-02",
"label" : "S.3.3.3#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a list of documents designating those authorized to act on behalf of the PHR Account Holder sorted by one or more defined data elements."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.3.3-03",
"label" : "S.3.3.3#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to tag a document designating those authorized to act on behalf of the PHR Account Holder as Active or Non-Active by category of document."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.3.3-04",
"label" : "S.3.3.3#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD maintain the document designating those authorized to act on behalf of the PHR Account Holder and/or a note that specifies that document’s location."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.